home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.eiffel,comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.modula2,comp.lang.modula3,comp.lang.smalltalk
- Path: news.sprintlink.net!eskimo!news
- From: hgeorge@eskimo.com (Harry George)
- Subject: Re: whither style
- X-Nntp-Posting-Host: tia1.eskimo.com
- Content-Type: Text/Plain; charset=US-ASCII
- Message-ID: <DKxv35.Lo2@eskimo.com>
- Sender: news@eskimo.com (News User Id)
- Organization: <none>
- X-Newsreader: WinVN 0.99.7
- References: <cmanDK7x13.5KM@netcom.com> <30e26364.2569895@news1.wolfe.net> <60SqRiBF3RB@herold.franken.de>
- Mime-Version: 1.0
- Date: Wed, 10 Jan 1996 00:09:04 GMT
-
- In article <60SqRiBF3RB@herold.franken.de>, jhd@herold.franken.de says...
- >
- [snip]
- >In my experience, such languages actually don't need HN; the compiler will
- >catch all errors that HN is supposed to help avoid. This is because in
- >these languages, the type of a variable or value precisely defines what
- >operations are admitted for it. If you had a type zero-terminated-string
- >in such a language, the compiler won't allow you to pass this to a routine
- >that expects a string with a length descriptor.
-
- In general I agree (e.g., for Modula-3). But if I am doing a binding for a
- library
- originally HN-encoded, I'll use the same naming convention. That makes
- it more familiar to the typical programmer who may just be trying
- out a "new language". However, once I get past the initial call,
- (e.g., for an object wrapper around those raw facilities), I go back
- to non-HN style.
-
- [snip]
- >
- >-Joachim
-
- --------------------
- Harry George
- email: hgeorge@eskimo.com
- smail: 22608 90th Ave W / Edmonds WA 98026
- quote: <under construction>
-
-